HAL CCB migration: List of applicable concepts ¶
This section provides information about the HAL CCB applicable architecture concepts.
Concepts for CCB ¶
|
Concept |
Description |
|---|---|
|
In HAL2,The
The CCB does not require global configuration, so there is no
The various CCB operations are still available through dedicated functions same as HAL1. |
|
|
The handle structure has been renamed to
|
|
|
The functions
|
|
|
Two functions to set and get user data are available:
|
|
|
The CCB state machine has been reworked to ensure transitions of the peripheral functional states. |
|
|
The HAL CCB functions were updated to return:
|
|
|
The error management function has been renamed to
|
|
|
All TypeDef parts of the HAL CCB driver have been removed and replaced by
|
|
|
Const keywords have been added to non-modifiable pointers to ensure that either the pointer itself or the data it points to cannot be modified. This enhances code safety and readability, prevents unintended modifications, and renders code more robust and maintainable. |
|
|
The
|
|
|
Replace Finite Parameter Defines (Including PPP Instances) with Enum Types at HAL Levels. |
Convert finite parameters, including CCB instances, into enumerated types (enums) at the HAL level to enhance code readability, maintainability, and type safety. |
|
Add HAL_PPP Prefix to All HAL Peripheral APIs (Defines, Macros, Types, and Functions). |
All HAL CCB functions start with
|